Periodic Functions Available to Schedule | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Working with Report Control (WRPT) |
Purpose: Use the About Application screen to review information about Order Management System.ó
How to display this screen: Select About from an Admin screen (such as the Document Management Screen, Forms Management Screen, Job Management Screen, Commands, or User Control screens).
System Information |
System Value |
Version |
The build number installed on the Order Management System Cloud Service application server, as defined in the CWDIRECTCP_VERSION property. The version displays in major.minor.patch format, where major is the major release number, minor is the minor release number, and patch is the patch release number. For example: • The major release for version 17.0 would display as 17.0.0. • A patch to release 17.0 would display as 17.0.1, where 1 if the patch release number. |
Operating System |
The version of the operating system you are using. |
Operating System Architecture |
The processing architecture used to run the Order Management System Cloud Service application. |
Java Version |
The version of Java used to run the Order Management System Cloud Service application. |
Java Vendor |
The vendor that provided the version of Java that runs the Order Management System Cloud Service application. |
Database Level |
The database level used to run the Order Management System Cloud Service application. The database level displays in major.minor.patch.databaselevel format, where major is the major release number, minor is the minor release number, patch is the patch release number, and databaselevel indicates the number of times a database update script has been run for the release. |
Internal Build |
The internal build number assigned to the EAR file used to run the Order Management System Cloud Service application. The build number displays in YYYYMMDDHHMMSSPM format, indicating the date and time of the build, with the last two positions indicating either AM or PM. |
Current Order Volume |
The order count for the current year. You can also run the Order Volume Report (OVOL) to generate the Order Count report, which provides the total number of orders entered in Order Management System Cloud Service broken out by company, and optionally, order type for a specified date range. Note: • Orders entered in a company flagged as inactive do not count towards the current order volume. If a company is flagged as inactive, the Menu Driver Screen displays a message indicating This company is flagged as inactive and should not be used to process live orders.See Working with Companies (WCMP) to review the Active company setting for a company. • If the originating location for a retail pickup or delivery order is Order Management System Cloud Service, the system does not increase the order count for the order. The system identifies the originating location as Order Management System Cloud Service if the request_system_cd in the fulfillment response message matches the system code in the OROB System (K50) system control value. In this situation, the system prefaces the E-commerce order number in the Order Header Extended table with ORIG#: 9999-001, where ORIG#: indicates the order was created as a result of OROB fulfillment assignment, 9999 is the order number, and 001 is the ship to number. |
Copyright |
Copyright information provided by Oracle. |
About Application Screen Options
Option |
Procedure |
Advance to the Document Management Screen |
Select My Docs. |
Advance to the Job Management Screen |
Select My Jobs. |
Advance to the Advanced Commands screen, where you can advance to working with user control records if you have sufficient authority |
Select Advanced commands. |
Return to the previous Order Management System Cloud Service screen |
Select Exit. |
Periodic Functions Available to Schedule | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Working with Report Control (WRPT) |
About Application OMSCS 18.1 April 2019 OTN